System And Method For Managing Content On A Network Interface

ABSTRACT

A web site may be present on the World Wide Web, an Internet location, an intranet location, an extranet location, or some other form of network interface. A system for automated management of content on a network interface can automatically create applications and links to those applications without human intervention. Examples of automated applications include newsroom applications, calendar of events, employment opportunities, project portfolio, biographies, frequently asked questions, document library, category management, product catalogs, e-mail broadcasts, surveys, and newsletters. Fully normalized hierarchies of business rules and user profiles can be supported by the system to facilitate automation and configurability. Multiple content providers can manager a single web site in a simultaneous or substantially simultaneous manner. Multiple organizations can use the system to manage multiple web sites in a substantially simultaneous manner.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/833,228 filed Mar. 27, 2020, which is a continuation of U.S. patentapplication Ser. No. 15/299,530 filed Oct. 21, 2016 (now U.S. Pat. No.10,606,930), which is a continuation of U.S. patent application Ser. No.14/329,228 filed Jul. 11, 2014 (now U.S. Pat. No. 9,141,720), which is acontinuation of U.S. patent application Ser. No. 14/263,383 filed Apr.28, 2014 (now U.S. Pat. No. 9,514,239), which is a continuation of U.S.patent application Ser. No. 12/270,354 filed Nov. 13, 2008 (now U.S.Pat. No. 8,713,134), which is a continuation of U.S. patent applicationSer. No. 10/366,168 filed Feb. 13, 2003 (now U.S. Pat. No. 7,472,170).The entire disclosures of the applications referenced above areincorporated by reference.

BACKGROUND

The invention is a system and method (collectively the “system”) for theautomated management of content on a network interface.

Businesses, government entities, non-profit organizations, socialgroups, religious organizations, universities, research institutions,individuals, and other entities (collectively “entities”) increasinglyrely on network interfaces such as web sites on the World Wide Web,Internet sites, intranet sites, extranet sites, and other networkinterfaces (collectively “web sites”) to communicate and interact withcustomers, potential customers, vendors, potential vendors, investors,potential investors, employees, potential employees, the general public,and other types of audiences (collectively “users”).

Despite the increasing importance of web sites, many web sites are outof date and as such, display inaccurate and potentially misleadinginformation. The challenge of keeping a web site up to date can be adifficult goal for even large entities with substantial resources. Forsmaller entities, keeping a web site up to date that is fully loadedwith information and functionality is typically not a realistic option.Smaller entities with correspondingly fewer resources and personnel,find it difficult to effectively manage the content on their web sitesdue to a limited number of personnel skilled in the technologies ofwebsite creation. Many organizations ultimately refrain from providingcontent-rich web sites because of the maintenance challenges, and theembarrassment of outdated information. Thus, time-sensitive informationis not displayed, the overall utility of the web site is reduced. Itwould be desirable if the content in web sites could be created,modified, and deleted in an automated manner. It would also be desirablefor a web site management system to allow non-technical contentproviders control the content of web sites without the intervention ofmore technical personnel.

Even in large entities, the personnel responsible for managing web sitesfrom an information technology perspective are often not the personsbest situated to manage the content of the web site. In the context ofweb sites that are “rich” in content, there may be several differentpersons or even groups of people, responsible for the management ofcontent. Thus, even the routine management of web site content canrequire multiple interactions and communications between various personsfilling various roles with the entity sponsoring the web site. For eachextra person involved in the management process, the number ofcommunication links can increase exponentially. It would be desirable tosave time and resources while at the same time reducing the possibilityfor errors by reducing the number of people needed to manage web sitecontent. It would also be desirable for a web site management system tosupport the allocation of content responsibilities decided by the entitysponsoring the web site.

Website management is further challenged by the desirability to maintainconsistency of style, format, color, and other aesthetics. Suchconsistency can be difficult to obtain when many different people areinvolved in a highly manual process. It would be desirable for a website management system to provide various templates to facilitate theuniform formatting of content.

There is no reason to believe that the existing art provides anysolutions to the problems discussed above. There is no suggestion ormotivation in the art to provide non-technical personnel with theability to control the information technology used to manage web sites.Moreover, the existing art affirmatively teaches away from such anapproach. Developments in web site technology focus on creating advancedfeatures requiring an increasingly sophisticated level of expertise.Developments in the art do not suggest the ability to providecustomizable and automated features in a simpler and less-technical waythat can be performed by fewer people.

SUMMARY

The invention is a system and method (collectively the “system”) for theautomated management of content on a network interface. The networkinterface can be a web site on the World Wide Web, an Internet location,an intranet location, an extranet location, or some other form ofnetwork interface location (collectively “web site”).

The system is a web site management system that allows non-technicalusers to control the content of a web site without the assistance oftechnical personnel.

Various applications and links pointing towards those applications canbe created and configured by the system in an automated fashion.Multiple non-technical content providers can manage the content of asingle web site at the same time, or in a substantially simultaneousmanner. Highly configurable business rules can be used to automate theadministration of the web site, and the management of web site content.

An interface subsystem can be used to capture the inputs ofnon-technical personnel, in varying content and administrativecapacities. A content system can be used to control, create, update,delete, schedule, and otherwise manage content in an automated fashionusing the instructions received from the interface subsystem. In someembodiments, an administrative subsystem can be used to create, modify,delete, and otherwise manage the business rules that govern thefunctionality of the system. A highly modular approach can be used tofacilitate a high level of automation with a high level of flexibilityand configurability.

Various aspects of the invention will become apparent to those skilledin the art from the following detailed description of the preferredembodiment and the drawings described briefly below.

BRIEF DESCRIPTION OF THE DRAWINGS

Some of the various features, advantages, uses, and characteristics ofthe present invention can become more apparent by referring to thefollowing description and drawings.

FIG. 1 is an environmental diagram illustrating one example of some ofthe elements that can be incorporated into the system, and subjected tothe processing of the system.

FIG. 2 is an architectural diagram illustrating one example of atechnical configuration of the system.

FIG. 3 is a block diagram illustrating one example of the differenttypes of data and information that can be input into the system.

FIG. 4 is a block diagram illustrating one example of a subsystem-levelview of the system, including an interface subsystem and a contentsubsystem.

FIG. 5 is a block diagram illustrating another example of asubsystem-level view of the system, including an administrativesubsystem.

FIG. 6 is a flow chart illustrating one example of a process flow thatcan be incorporated into the system.

FIG. 7 is a block diagram illustrating one example of the differenttypes of applications that can be incorporated into the system.

FIG. 8 is a multi-threaded process flow diagram illustrating one exampleof a portal setup process.

FIG. 9 is a multi-threaded process flow diagram illustrating one exampleof how various interfaces can be used to interact with the system inmanaging a web site.

FIG. 10 is a multi-threaded process flow diagram illustrating oneexample of the processing that can be performed by a document managementapplication incorporated into the system.

FIGS. 11, 12, and 13 are partial object diagrams that in the aggregate,illustrate one example of the some of the objects that can beincorporated into the system.

FIG. 14 is a data diagram illustrating one example of some of the database tables that can be incorporated into the system.

DETAILED DESCRIPTION

The invention is a system and method (collectively the “system”) forautomatically creating, updating, scheduling, removing, and otherwisemanaging content accessible from a network interface, such as anInternet location (“Internet site”), an intranet location (“intranetsite”), an extranet location (“extranet site”), a web page on the WorldWide Web, or any other form of network interface (collectively “website”).

I. Introduction of Elements and Definitions

FIG. 1 is an environmental diagram illustrating one example of some ofthe elements that can be incorporated into a web site management system20. The system 20 can be incorporated into a wide variety of differenttechnical, organizational, and business environments. In someembodiments of the system 20, the technology supporting the system 20 ismanaged by a third party such as an Application Service Provider (ASP)or some other third party (collectively “third party arrangements”). Inthird party arrangements, entities benefiting from the system 20 can becharged on a subscription basis, a traffic-based charge, or some othertransaction type. In other embodiments, the system 20 is hosted andsupported by the organization providing the content to the web site.

A. Content Providers

A content provider 22 is potentially any person, machine, device orsystem that is responsible for providing content to a web site. In apreferred embodiment, the content provider 22 is a person responsiblefor managing web site content. The content provider 22 need not possesstechnical skills relating to the creation, modification, or deleting ofweb sites in order to use the system 20. There can be a wide variety andnumbers of content providers 22 that interact with the system 20. Inpreferred embodiments involving multiple content providers 22, differentcontent providers 22 are responsible for different applications on theweb site.

In some embodiments, the content provider 22 can be an expert system, aneural network, a device incorporating artificial intelligence, or someother intelligence technology (collectively “intelligence technology”).

Content providers 22 can include administrators responsible forcreating, updating, deleting, and scheduling the business rules thatgovern the functionality of the system 20.

The content provider 22 provides content to the system by providing aninput 24 to a content interface 26.

B. Input

Input 24 is potentially any interaction or omission between the contentprovider 22 and the content interface 26 that can be captured,understood, received, or otherwise observed by the system 20. Input 24can also be referred to as input characteristics or input attributes.

A single embodiment of the system 20 can be capable of capturingmultiple inputs 24 in a wide variety of different formats and through awide variety of different mediums.

Input mediums can include typing of data using a keyboard, speaking intoa voice recognition component, clicking a mouse, failing to respond to aprompting of the system 20 in a particular period of time, importing ofa file, receiving sensor readings, or any other potential medium(collectively “input mediums”).

Inputs 24 can also include a wide variety of different data types. Text,numbers, sound, still pictures, multi-media displays, and any other typeof data characteristic (collectively “input types”) can be used as theinputs 24 of the system 20.

C. Content Interface

The content interface 26 is any interface capable of receiving input 24from the content provider 22. In preferred embodiments, the contentinterface 26 utilizes includes some form of a graphical user interface.

The content interface 26 can be housed in any device capable ofaccessing a network site 34. The content interface 26 can be housed in adesktop computer, a laptop computer, a work station, a pager, a server,a mini-computer, a mainframe computer, a data terminal, a cell phone, apersonal digital assistant (PDA), a programmable logic device, anembedded computer, a cable TV or satellite TV interface, or any othercommunication device that can access the network site 34. Multiplecontent interfaces 26 of different types can interact with the system 20in a simultaneous manner.

The content interface 26 can include both an input view and an outputview. The input view allows the content provider 22 to provide input 24to the content interface 26. The output view allows the content provider22 to view the input 24 as entered into the input view. In a preferredembodiment, the content interface 26 includes a portal that allows thecontent provider 22 to access the input view and the output view in asimultaneous or substantially simultaneous manner. In preferredembodiments, the content interface 26 is platform independent withrespect to the underlying information technology architecture. Thecontent interface 26 provides a flexible, innovative, and highlyconfigurable hierarchy to manage content on the network site 34. Contentproviders 22 can be provided with granular access to content on thenetwork site 34 through the use of the content interface 26.

The content interface 26 can also include application view for viewingthe inputs 24 and outputs of an application 30 managed by the system.The application view can include an input application view and an outputapplication view.

The content interface 26 receives the input 24 from the content provider22 and transmits the input 24 to a computer system 28 housing theprogramming logic that allows the system 20 to function.

D. Computer

The computer or computer system (collectively the “computer”) 28 is anydevice capable of housing the programming logic that allows the system20 to function. The computer can be a stand alone computer, a server, amainframe computer, a mini-computer, a web server, an Internet server,an intranet server, an extranet server, a local area network (LAN), awide area network (WAN), a wireless network, or any other form ofcomputational device. The computer 28 can include ancillary devices andcomponents commonly used in conjunction with the computer 28 itself. Insome embodiments, the computer 28 is the same device that houses thecontent interface 26.

The computer 28 can create, update, delete, or schedule (collectively“manage”) an application 30 on the network site 34. In a preferredembodiment, there are many different applications 30 being created,updated, deleted, and scheduled at various times by various contentproviders 22. Applications 30 can be managed in an automated fashionwithout human intervention. Applications 30 processed by the system 20are stored in one or more network sites 34.

The computer 28 can also create, update, delete, or schedule(collectively “manage”) one or more links 32 on the network site 34pointing to the various applications 30.

E. Application

An application 30 is a unit of content provided on the network site 34.Applications 30 can include executable software programs, opportunitiesto exchange data with an outside user 50, files, text, graphics, sound,and other forms of applications 30. Applications 30 may interact withvarious databases.

Examples of applications 30 that can be incorporated into the system 20include but are not limited to: a newsroom application; an eventsapplication; an opportunity application; a project application; acatalog application; a communications application; a survey application;a newsletter application; a document library; a publicity application; afrequently asked questions application; an about us application; and athird party links application. The various applications 30 that can beincorporated into the system 20 are disclosed in greater detail below.

Applications 30 can be leveraged to support business-to-business,business-to-consumer, and internal business operations.

Applications 30 can be managed automatically by the system 20 withouthuman intervention. Multiple applications 30 on a single networklocation 34 can be managed by multiple content providers 22 in asimultaneous or substantially simultaneous manner. Applications 30 canbe as fully configurable as allowed by the business rules incorporatedinto the system 20. Configurable applications 30 are those applications30 that can be modified or configured by the content provider 22. Someconfigurable applications 30 can also be configured to some degree bythe users 50 with respect to how the application performs for that user50. For example, a user 50 can sign up to receive an e-newsletter in aparticular format, such as HTML, PDF, JPEG, etc.

F. Links

A link 32 is the mechanism by which the user 50 of a network site 34activates the application 30. Links 32 can encapsulate an URL (uniformresource locator), a TCP/IP address, of any other form of identifyingthe location of applications 30 on the network site 34.

Links 32 can be managed automatically by the system 20 without humanintervention. Multiple links 32 on a single network location 34 can bemanaged by multiple content providers 22 in a simultaneous orsubstantially simultaneous manner. A configurable link 32 is a link 32that can be modified or configured by the content provider 22 aspermitted by any relevant business rules. A configurable link 32 can bea static code program.

A links display page in the content interface 26 can be used to displaythe generated link 32 for a specific application 30 selected by thecontent provider 22. The link 32 can include any necessary parametersand formatting.

G. Network Site and Network Locations

The system 20 can be implemented on a wide variety of differentnetworks. Multiple networks can be incorporated into a single embodimentof the system 20. The network can be the Internet, the World Wide Web,an intranet, an extranet, a local area network (LAN), a wide areanetwork (WAN), or any other form of network (collectively “web site”).The network site 34 can be identified by an URL, a TCP/IP address, orsome other form of address.

The network site 34 is made up of one or more locations 36. Just as aweb site can include a wide variety of different web pages and areas onthose pages, there can be a wide variety of different types of locations36 on a single network site 34.

H. Access Devices

An access device 38 is any device capable of accessing the network site34. Some access devices 38 are content provider 22 access devices thathouse content interfaces 26.

Access devices 38 can also be user access devices. A user access deviceis an access device 38 that is used by a user 50 to access the contenton the network site 34. The same access device 38 can serve as both auser access device and a content provider access device because the typeof access device is determined by the nature of the interaction with theaccess device 38.

Access devices 38 can include a pager 40, a cell phone 42, a PDA 44, alaptop terminal 46, a desktop terminal 48, or any other device capableof accessing the network site 34.

I. Users

A user 50 is potentially any person, search engine, automated engine, ordevice interacting with the system 20 for the purpose of using oraccessing the content on the network site 34. Users 50, in contrast tocontent providers 22, do not control the content of the network site 34unless the network site 34 includes an application 30 that managescontent on the network site 34 in accordance with the user'sinteractions with the network site 34. A message board of comments wouldbe one example of the impact a user 50 could have on the system 20.

A user 50 in one context may be a content provider 22 or anadministrator in another context. As illustrated in the figure, thereare a wide variety of different types of users 50. Users 50 can beinternal to the organization controlling the network site 34, and users50 can be outsiders to the organization controlling the network site 34.

II. User and Administrator Views

FIG. 2 is an architectural diagram illustrating one example of atechnical configuration of the system 20.

The underlying information technology structure of the system 20 cansupport a user-view 51 and an administrator-view 23. In a preferredembodiment, there are at least two primary categories of views. In someembodiments, there is a separate and distinct content-provider viewrelated to content management, in contrast to the administrator-view 23which can then be limited to business rule management. In otherembodiments, the administrator-view 23 can also be referred to as acontent-provider view.

A. User-View

One category of views is the user-view 51. Users 50 access the user-view51 through one or more of the access devices 38 described above. Theconnection between users 50 and the system 20 may be secure ornon-secure. Some user-views 51 may be purely passive, such as thenavigation of a “passive website.” Other user-views 51 may include theability to perform transactions, or trigger other “active” processing.The ability to perform more active processing may require a secureconnection. The user-view 51 interacts with a network 52. In a preferredembodiment, the network 52 is a web site or some form of web page.

Through the user-view 51, various applications 30 on the network 52 canbe accessed. An appview.asp 54 is a view of one or more applications 30that are accessible through the user-view 51. Some applications 30 willinvolve an underlying application engine 58 to perform certainfunctionality and even access a database 70. For other applications 30,such as the appview.asp at 56, the applications 30 may be more passivein nature, not requiring any type of executable engine or data baseaccess.

B. Administrator-View

The other category of views is an administrator-view 23. Theadministrator-view is connected to the network 52 through a secureconnection so that the content and/or business rules of the system 20can be managed. An administrator console 60 or administrator portal isused to manage the applications 30 and/or business rules of the system20. The administrator-view 23 can include both an input view and anoutput view. By means of example only, the administrator console 60 isshown controlling a newsroom/press release application 62, a newsletterapplication 64, a portfolio application 66, and a broadcast application68. The various applications 30 that can be incorporated into the system20 are disclosed in greater detail below.

All of the various applications 30 can interact with the database 70 asdesired to facilitate the functionality of the applications. Theadministrator-view 23 can be created using a wide variety of differentarchitecture characteristics. In preferred embodiments, anobject-oriented design structure is incorporated. The portal engine canutilize a combination of active server page technology, XML, customstyle sheets, and database interactions to provide access to specificapplications 30 links 32 for users 50 and groups of users 50.

The administrator-view 23 can be used to allow users 50 and groups ofusers to have highly configurable templates based on the individualneeds of the users 50.

C. Other Architecture Characteristics

The system 20 can be built upon a wide variety of different informationtechnology environments. In a preferred embodiment, active server pagetechnology is used. Java or the Java scripting language can be used tomake the system 20 “browser agnostic” and platform independent to users50. Each functional area of each application 30 can be broken down intoa set of active server page modules.

In a preferred embodiment, the database 70 is a relational database. Inalternative embodiments, the database 70 can be an object-orienteddatabase, a binary database, a series of flat files and arrays, or someother data storage arrangement. In a preferred embodiment, all database70 logic and queries are encapsulated in the form of stored procedures.

III. Input Characteristics

FIG. 3 is a block diagram illustrating one example of the differenttypes of data and information that can be input into the system. Theflexibility of system 20 is in part related to the variety of inputs 24that can be incorporated into the system 20.

A. User Characteristics

A user characteristic 72 is potentially any characteristic relating tothe user 50. It can include user profiles; login requirements; past useof the system 20; affiliation with various organizations, groups, orsubgroups; an e-mail address or other contact information; or any otherattribute relating to the user 50.

B. Start Date

Applications 30 can be configured to begin on a particular date/timethat is referred to as a start date 74. For example, a particularproduct promotion may be scheduled to occur in the future. The contentprovider 22 can provide the relevant content to the system 20 before thepromotion date because a start date 74 for the promotional content willallow the system 20 to schedule the display of the promotional contentat the appropriate day and time.

C. End Date

Applications 30 can also be configured to end on a particular date/timethat is referred to as an end date 76. In the example of a productpromotion, the expiration of the program can be inputted into the system20 in advance so that out of date promotional materials will not bedisplayed on the network site 34. The start date 74 and end date 76 forcontent and applications 30 can be entered by the content provider 22 atthe time in which the content itself is entered, or those inputs 24 canbe provided at a later date.

D. Application Characteristics

Application characteristics 78 can include potentially any attributerelating to an application 30. Application characteristics 78 caninclude start dates 74, end dates 76, and other inputs 24, includingother inputs 24 displayed in FIG. 3.

E. Business Rules

A business rule 80 is any rule incorporated into the system 20 thatcontrols how the system 20 functions. For example, business rules 80 maycontrol how content providers 22 interact with the content interface 26,or how multiple content providers 22 may manage different applications30 in a simultaneous or substantially simultaneous manner.

Business rules 80 can exist at many different levels of the system 20. Abusiness rule set by an ASP can be referred to as an ASP-based businessrule. A business rule effective an entire organization can be referredto as an organization-based business rule. A business rule that appliesonly to a group within an organization can be referred to as group-basedbusiness rule. A business rule that applies only to a sub-group of agroup can be referred to as a sub-group-based business rule. A businessrule that applies to users 50 can be referred to as a user-basedbusiness rule. Business rules can exist at multiple levels at the sametime. User profiles can similarly exist at these various levels, and areclosely related to business rules. Many business rules can utilizeprofiles to impact the processing that is performed.

F. Organization Characteristics

An organization characteristic 82 is potentially any characteristic orattribute relating to an organization. An organization or entity can becomposed of various groups, subgroups, and personnel. An organization orentity can also have relationships and roles with other organizations,such as customer, vendor, regulator, competitor, etc.

G. Transaction Characteristics

A transaction characteristic 84 is potentially any characteristic orattribute relating to a transaction. Transaction characteristics 84 caninclude buyers, sellers, payors, payees, transaction types, transactionitems, monetary amounts, payment terms, jurisdictions, and virtually anyother characteristic or attribute.

H. Content Provider Characteristics

A content provider characteristic 86 is potentially any characteristicor attribute describing or relating to a content provider 22. It caninclude profiles; login requirements; past use of the system 20;affiliation with various organizations, groups, or subgroups; an e-mailaddress or other contact information; authorization levels; or any otherattribute relating to the user 50.

I. Events

An event 88 is potentially any occurrence (or representation of anoccurrence) in the system 20 that can serve as a trigger or distinctionfor some other process in the system 20. For example, the expiration ofa product promotion can be an event 88 in the system 20 that couldtrigger the beginning of a new product promotion. Business rules 80 canuse events 88 to further automate and configure the system 20.

IV. Subsystem-Level View

FIG. 4 is a block diagram illustrating one example of a subsystem-levelview that includes an interface subsystem 90 and a content subsystem 92.As illustrated by the two-directional arrow, processing can bounce backand forth between these two subsystems.

A. Interface Subsystem

An interface subsystem 90 can be responsible for all system 20interactions with the outside world, including users 50, contentproviders 22, and administrators. A user 50 can interact with theinterface subsystem through a user-interface, a content provider 22 caninteract with the system 20 through a content provider interface (orcontent interface 26), and an administrator can interact with the system20 through an administrator interface.

The interface subsystem 90 is configured to capture various inputs 24that are used by the system 20 to automatically create configurableapplications 30 and configurable links 32. The system 20 canautomatically embed the configurable links 32 in accordance withapplication characteristics 78, such as start dates 74 and end dates 76,as well as other forms of input 24. The various configurable links 32point the various configurable applications 30.

The end date 76 received by the interface subsystem 90 can be used bythe system 20 to trigger the automatic removal of an application 30 fromthe network site 34 on the date and time indicated by the end date 76.

The interface subsystem 90 can include multiple content interfaces 26for capturing input 24 at the same time, or in a substantiallysimultaneous manner. The interface subsystem 90 allows content providers22 without information technology expertise, to manage the network site34. The various applications 30 can have different start dates 74 andend dates 76. Different content interfaces 26 can be used to createdifferent applications 30 and links 32 on the same network site 34 in asimultaneous or substantially simultaneous manner. Business rules 80 canimpact how applications 30 and links 32 are managed by the system 20.

As discussed above, profiles can be used by the business rules 80 of thesystem 20 to automate functionality while at the same time supportingthe ability to customize the functionality of the system 20. Profilesare associated with the system 20 through the particular interfaces ofthe interface subsystem 90 used by those various persons. Profiles canbe ASP-level profiles, organization-level profiles, group-levelprofiles, sub-group-level profiles, and user-level profiles. If thesystem 20 is provided in a third party arrangement to organizations on asubscription basis, a subscriber profile can also be incorporated intothe system 20. In a third party arrangement, multiple organizations canmodify their various network sites 34 in a simultaneous or substantiallysimultaneous manner.

B. Content Subsystem

A content subsystem 92 includes all of the applications 30 and links 32on the network site 34 as well as the network site 34 itself. Contentsubsystems 92 can be configured in a wide variety of different ways,including all possible combinations of applications 30 and links 32 thatcan be managed by the system 20.

The various applications of the content subsystem 92 are described ingreater detail below. Users 50, content providers 22, and administratorsinteract with the content subsystem 20 through the interface subsystem90. The functionality of the content subsystem 92 can be performed in anautomated manner without human intervention after the receipt of theinput 24 from the interface subsystem 90.

C. Administrator Subsystem

FIG. 5 is a block diagram illustrating another example of asubsystem-level view of the system, including an administrativesubsystem 94. The administrative subsystem 94 can be used by variousadministrators to configure the business rules of the system 20 in thesame way that the content subsystem 92 controls the management of thecontent or applications 30 of the system 20. Business rules 80 controlhow persons such as users 50 and content providers 22 interact with thesystem 20. Business rules 80 can incorporate a high degree offlexibility, because they can be created and enforced at variousdifferent levels in an overlapping fashion.

V. Overall Process Flow

FIG. 6 is a flow chart illustrating one example of a process flow thatcan be incorporated into the system 20.

At 100, a profile can be defined. The profile can relate to a user, asubgroup, a group, an organization, or even an ASP. Profiles candetermine what menu options are visible, enabled, disabled, etc.Profiles also impact the application of business rules 80 by the system20. The system 20 can support a complex hierarchy of profiles.

At 102, a business rule 80 can be created or defined. An example of abusiness rule 80 would be that a particular group within an organizationcould only modify certain applications 30 on the network site 34 of theorganization. The system 20 can support a complex hierarchy of businessrules 80. In some embodiments, business rules 80 at a higher levelwithin the system 20 can be used to override business rules 80 set atlower levels. In other embodiments, lower level business rules 80 trumphigh level business rules 80 because the lower level business rules 80are more specifically tailored.

At 104, a start date 74 for a particular application 30 is scheduled. Anend date 76 could also be scheduled in the same interaction with thesystem 20. In some embodiments, multiple start dates 74 and end dates 76can be entered at the same time for multiple applications 30 and links32.

At 106, content for the various applications 30 and links 32 arecaptured using the interface subsystem 90. Inputs 24 as discussed above,can come in a variety of different mediums, formats, and data types.

At 108, the system 20 can automatically create, modify, or delete one ormore applications 30. Links 32 to the created or modified application 30can similarly be created or modified, and links 32 to deletedapplications 30 can similarly be deleted.

At 110, links 32 pointing to the active applications 30 can beautomatically embedded into the network site 34. In a preferredembodiment, the network site 34 is preformatted with respect to thelocations of certain applications 30, and the network site 34 caninclude a predefined or pre-formatted navigation tool or structure suchas a menu to facilitate user 50 navigation.

VI. Application-Level View

FIG. 7 is a block diagram illustrating one example of the differenttypes of applications 30 that can be incorporated into the system 20.Each of the illustrated applications 30, as well as other applications30 incorporated into the system 20, can be housed in the computer 28 orcomputer system 28 that houses the logic for the automated applicationand link generation process. The exact configuration of applications 30can vary widely from embodiment to embodiment. As web site practicesevolve over time, the number and types of applications 30 can similarlyevolve.

A. Newsletter

A newsletter application 120 can be used by an organization todistribute information about itself to persons inside and outside theorganization. A newsletter application 120 can be limited to individualpress releases or articles. In other embodiments, the newsletterapplication 120 can also include the active distribution of anelectronic newsletter that includes various articles or press releasesbundled together in the unit of a newsletter. The newsletter canincorporate different categories of stories, and can be configured toaccommodate profile information relating to the recipient or viewer ofthe newsletter. Images, sounds, and other non-text data can beincorporated into the newsletter application 120. The newsletterapplication 120 can include links to content on public third partynetworks, such as public web sites.

Articles can be searched and edited through the use of the newsletterapplication 120. Articles can be organized into a hierarchy ofcategories based on the subject matter, intended audience,organization-hierarchy, and virtually any other characteristic orattribute relating to the articles.

B. Events

An event application 122 can be responsible for displaying andscheduling relevant events 88. The business rules 80 can automaticallyinvoke certain processing based on events 88. For example, a specialtype of promotion may automatically trigger the sending out of an e-mailannouncement. Profiles can also determine the types of events 88 thatcan be viewed by a particular user 50. For example, if an event 88 isonly relevant to users 50 of a particular subgroup, the business rules80 may hide the event 88 from other users 50. Event minutes can becreated and displayed using the event application 122.

Events 88 can be added, updated, deleted, and scheduled using the eventsapplication 122. Events 88 can be organized into a hierarchy ofcategories based on the subject matter, intended audience, and virtuallyany other characteristic or attribute relating to the event 88.

C. Opportunity

An opportunity application 124 can provide a means for communicatingemployment opportunities, transaction opportunities, and other types ofopportunities specifically identified on behalf of an organization orsome sub-unit of the organization.

Opportunities can be added, updated, deleted, and scheduled using theopportunities application 124. Opportunities can be organized into ahierarchy of categories based on the subject matter, intended audience,and virtually any other characteristic or attribute relating to theopportunity.

D. Project

A project application 126 can also be referred to as a project portfolioapplication 126. The project application 126 provides a mechanism fororganizations and sub-units of organizations to create, update, anddelete information about various projects. Some projects can be open topublic view while others are limited to internal users 50. Projects canbe organized into a hierarchy of categories based on the subject matter,intended audience, and virtually any other characteristic or attributerelating to the project. Links for additional information can beprovided, as well as image files containing detailed project schedules.

Projects can be made visible/invisible on a case by case basis by anadministrator, or the visibility of projects can be determined bybusiness rules relating to the organization or sub-unit of theorganization.

E. Document Library

The purpose of a document library 128 is to provide a mechanism topublish documents of various types within an organization's web site fora targeted user, subgroup, group, or organization. In preferredembodiments, once a document is published outside the public group, itcan then be assumed that it will be secured pursuant to extranetfunctionality. Documents can be searched, edited, created, and deletedusing the document library application 128.

Documents can be added, updated, deleted, and scheduled using thedocument library 128. Documents 88 can be organized into a hierarchy ofcategories based on the subject matter, intended audience, and virtuallyany other characteristic or attribute relating to the document.

F. Communications

A communication application 130 can be used by users 50 to interact withthe organization sponsoring the web site. The communications of thecommunication application 130 can include a frequently asked questionsmodule, a broadcast module, and other types of passive and activecommunications. The broadcast module can include communications bye-mail, instant messaging, chat room posting, automated telephone calls,facsimiles, printed materials, letters, radio communication, satellitecommunication, or any other mechanism for transmitting information orinteracting with others (collectively “communications”). The businessrules 80 can trigger the automatic transmission of communications basedon events 88, user provided information, or any other attribute orcharacteristic tracked by the system 20.

Communications can be added, updated, deleted, and scheduled using thecommunication application 130. Communications can be organized into ahierarchy of categories based on the subject matter, intended audience,and virtually any other characteristic or attribute relating to thecommunication.

G. Survey

A survey application 132 can be used to capture survey data from bothinside and outside the organization sponsoring the web site. Surveys canbe created, modified, and deleted using the survey application 132.Survey results can be displayed using the survey application.

Surveys can be organized into a hierarchy of categories based on thesubject matter, intended audience, and virtually any othercharacteristic or attribute relating to the survey. Surveys can betargeted to particular users 50, and can relate to particular sub-unitswithin an organization. For example, different divisions of theorganization may collect customer satisfaction data independently ofother divisions.

H. Catalog

A catalog application 134 provides an organization with the ability tokeep an updated catalog of products and services on their web site. Insome embodiments, the catalog can interface with transaction enablingtechnologies to allow users 50 to make purchases online.

Catalogs can be organized into a hierarchy of categories based on thesubject matter, intended audience, and virtually any othercharacteristic or attribute relating to the various offerings. Catalogscan be configured and customized to reflect the interests, roles, andprofiles of particular users 50.

I. Biographies

A biography application 135 can be used to provide biographicalinformation about persons and groups of persons involved in theorganization sponsoring the web site. The format of the biographies canbe determined by a business rule 80.

Biographies can be added, updated, deleted, and scheduled using thebiography application 135. Biographies can be organized into a hierarchyof categories based on the subject matter, intended audience, andvirtually any other characteristic or attribute relating to thebiography.

The biography application 135 can display reporting relationships,direct phone numbers, subgroup affiliation, roles, contact information,and other useful information.

In some embodiments, the determination of whether a biography is to bedisplayed is done in accordance with a business rule 80 applying to theorganization or some sub-unit of the organization. In other embodiments,the business rules 80 can provide the determination be made on acase-by-case basis by an appropriate administrator. In such embodiments,the display of biographies need not be consistent in accordance withsome overall rule.

J. Publicity

A publicity application 136 allows an organization to manage pressreleases, advertising, and other forms of promotions (includingpotentially electronic coupons). In some embodiments, the functionalityof the publicity application 136 performed by some of the otherapplications 30 identified above.

Publicity items can be added, updated, deleted, and scheduled using thepublicity application 136. Publicity items can be organized into ahierarchy of categories based on the subject matter, intended audience,and virtually any other characteristic or attribute relating to thepublicity.

In preferred embodiments, the functionality of the various applications30 can be customized and automated in accordance with the business rules80. Business rules 80 determine what can be viewed, and by whom.Business rules 80 can incorporate a fully normalized processingstructure, so that processing elements are treated differently only tothe extent that there are differences, and that processing elements aretreated similarly only to the extent that there are similarities.

VII. Specific Sub-Processes A. Portal Setup

FIG. 8 is a multi-threaded process flow illustrating one example of aportal setup process implemented by an administrator. This process canbe referred to as a portal setup heuristic. In the example, the system20 is managed by an ASP or some similar third party. Members are contentproviders 22 for organizations that subscribe to the system 20 providedby the ASP. The process of FIG. 8 will be performed by the ASP if thenew member is an entirely new organization or subscriber. After anadministrator for the new organization or subscriber is setup, theadministrator can perform a similar process for other administrators andcontent providers 22 belonging to the organization. In non-ASP andnon-third party embodiments, there may be differences with respect tothe processing disclosed in FIG. 8.

Membership information for configuring the portal can be created at 201.If that information does not include a valid e-mail address at 202, thesystem 20 can prevent the process from moving on to subsequentprocessing. Alternative embodiments may implement different processingrules.

At 204, the administrator can define the member as being either activeor inactive. If the member is not active, the system 20 at 206 can storethe member information as inactive. In some embodiments, an inactivestatus will terminate the process. In other embodiments, the process cancontinue even if the member will not be active immediately.

At 207, the administrator sets the security level for the member if asecurity level does not currently exist. The security level can bestored at 208.

At 210, group information can be created. A single member can belong toseveral groups, and possess several roles. In an ASP embodimentinvolving a new customer, the first group should be at theorganization-level for the new subscriber.

Password expiration business rules can be set at 212. A license countcan be performed at 214 in an embodiment involving a third partyarrangement. At 216, the administrator can identify whether or not themember being created belongs to a group that is in fact a child ofanother group. If the new group is to be a child group, a display ofavailable parent groups can be displayed at 218. The administrator canselect the appropriate parent at 218, and that information can be storedat 220.

The administrator, or in some cases the system 20, determines whether ornot the group is an active group at 222. If the member is associatedwith an inactive group, all of the member information can be stored asinactive at 224. Otherwise, header information can be created at 226.Headers are stored in a header table that is described in greater detailbelow. Network sites 34 can be divided up into sections. Headers can beassociated with the various sections. Headers can be used to describethe various categories of data in a system 20 that preferablyincorporates a hierarchical and compartmentalized data design.

Link 32 information for the various applications 30 can be entered bythe administrator or content provider 22 at 228. At 230, a determinationis made by either the administrator/content provider 22 or by thebusiness rules 80 of the system 20, as to whether a particular link isprivate or public. That determination is stored at 232. That samedetermination can be applied to other groups at 234, with the selectedgroups being stored at 236.

Headers can have a status independent of the groups to which the headersare affiliated. The status of the header is either set or evaluated at238, and stored at 239.

Application links 32 can be assigned to headers at 240. Only activelinks can be assigned to active headers. The various application link toheader relationships can be stored at 242. Application links 32 can thenbe associated with various groups at 244. The application to grouprelationships are then stored at 246. Headers can then be assigned togroups at 248, with those relationships being stored at 250.

Members can then be associated with one or more groups at 252, withthose relationships being stored at 254. The activation of a particularapplication occurs at 256, where available applications 30 can beactivated on member by group basis. The storage of application to memberby group information occurs at 258.

At 260, a portal template can be assigned. The interface subsystem 90can provide a wide variety of templates to start from, and additionaltemplates can be created from scratch or from the modification ofexisting templates. Template styles can be assigned at 262. Templatestyles do not affect the substance of any application 30 or thefunctionality of the system 20. Rather template styles allow the portalsto be configured to the aesthetic tastes of the content provider 22 oradministrator using the portal. Template styles can resemble the choicesmany GUI operating systems provide users with respect to fonts, onscreen control devices (radio buttons vs. check boxes) etc. Portalbranding can be assigned at 265 and portal colors can be assigned at268. At all steps of assigning attributes to the portal, data can besaved at 261.

B. Content Management

FIG. 9 is a multi-threaded process flow illustrating one example of howvarious interfaces can be used to interact with the system in managing aweb site. This process can be referred to as an interactive heuristic.There are four content provider/administrative functions disclosed inFIG. 9. A system administrative console at 340 can be used to set systemattributes such system-level business rules 80 at 342. A system portalmanager at 350 can be used to set system attributes relating to theportal at 352. A system content manager at 370 can set, modify, orremove content attributes at 372. A system style manager at 360 can setstyle attributes at 362 that are then propagated throughout the systemat 364. These different functions can be performed in a simultaneous orsubstantially simultaneous manner, in accordance with the business rules80 incorporated into the system 20.

For all roles of content providers 22 and administrators, access to thesystem 20 begins with a login process at 301. If that process is notsuccessful at 304, the login attempts can be limited at 306 to somepredefined number or to some number dynamically determined by thebusiness rules 80. The person attempting to access the system 20 can beprompted at 302 if the password has been forgotten. The existing artincludes many techniques and methodologies for dealing with persons whohave forgotten their passwords. If a password at 308 is determined to beexpired, a change password interface can be invoked at 310 to create anew password.

Once the person is logged in, a list of available groups can bedisplayed at 311. The list is contingent upon the security accessassociated with the logged in persona. A group can then be selected at312. Application links for the current group can be obtained at 314. Theassigned template(s) can be obtained and applied for the group at 318.The assigned branding and colors can then be obtained and applied at320.

After step 320, the process steps depend on the particular reason forthe person logging in, and the role of that person. The system 20 canobtain active news items at 322 so that the style selected at 362 can beapplied to the newsroom at 324. Active events can be obtained at 326 sothat changes in style can be applied at 328.

If the purpose of logging in is to modify content, the content items canbe obtained at 330 with a new navigation bar being displayed at 332. Theupdated version of the content can be previewed at 334 before changesare actually made to the system 20.

C. Document Management

FIG. 10 is a multi-threaded process flow diagram illustrating oneexample of the processing that can be performed by a document managementapplication incorporated into the system. This process can be referredto as a document management heuristic.

The four general categories of processing are a search document step at401, an add document process at 460, a maintain file types by groupmethod at 470, and a view document by group function at 490.

Documents can be searched at 401 through the use of search criteria. Insome embodiments, the system 20 can improve the search criteria suppliedby the system 20 by using online dictionaries that include synonyms ofthe terms in the search criteria. The search results can be viewed at402, where a particular document can also be selected for subsequentprocessing. At 404, a document can be edited, which preferably creates ahistory of change document to memorialize document history. After step404, the process for adding a new document is the same as for changingan existing document.

A file name can be selected at 406. The document will also need to beassociated with a valid file type. File types are maintained by group at470. The relationship between files types and groups are stored at 472.If the file type at 410 is not valid, for whatever reason, the processloops back to the selection of a valid file name at 406.

If the file type is valid at 410, the process continues to theestablishment of effective dates at 412. Start dates 74 and end dates 76are stored at 480. That thread then continues on to step 442, which ispart of the view documents by group processing that can be invoked at490, and is described in greater detail below.

Documents can be assigned to available/active categories at 414.Categories are stored on the categories table described below, and canbe a powerful tool in compartmentalizing the functionality and data ofthe system 20. Logical categories can be created at any time in theprocess at 482 before they are needed to be associated to documents.Category permissions can be assigned to groups at 484. This results in alist of available categories by group at 486 for which a category can bechosen at 414.

The status of the document is either checked or set at 416. If thestatus is inactive, that status can be stored as inactive at 488. Iffile compression is deemed desirable at 418 by the system 20 or by theuser 50, then a file compression routine can be invoked at 419. Thedocument attributes and physical file can be stored at 420.

At 422 a determination is made as to whether the document is to beaccessible to particular groups or to particular members (individuals).If access to the document is to be limited to a particular list ofmembers, then a list of active members is pulled at 430 allowing thedocument to be assigned to one or more of the members at 432. All memberto document relationships can be stored at 434 before processing ends.

If the document is to be accessible to entire groups, a list of activegroups is obtained at 424. A selection is made at 426, assigning thedocument to one or more of the groups. All relationship information canthen be stored at 428 before the process ends.

It can be desirable to view documents by group, especially from anadministration standpoint. This process is invoked at 490. A list ofactive documents by group can obtained at 492. The effective dates ofthose documents can be obtained at 442. Document categories areidentified at 444. Document security can be checked at 446. A particulardocument can then be selected at 448. Document viewer information can beobtained at 454. Viewers are assigned to groups at 450. The relationshipbetween groups and document viewers can then be saved at 452 and used at454. An audit record of all persons accessing the document is createdand updated at 456 before the process terminates.

VIII. Object-Level View

FIGS. 11, 12, and 13 are partial object diagrams that in the aggregate,illustrate one example of the some of the applications that can beincorporated into the system 20.

A. Login Page

A login page object 502 may be used by a content provider 22 to accessthe management functionality provided by the system 20. Profiles androles can be attributed to the person logging in using the login pageobject 502.

B. Portal Engine

A portal engine object 504 is the mechanism by which the content of theweb site is added, updated, deleted, and scheduled. The portal engineobject 504 provides the ability to configure the various applications 30of the system 20.

1. Newsroom

A newsroom object 510 allows the content provider 22 to manage anewsroom application. The newsroom application can be used to managepress releases and other forms of communications. An add news itemobject 512 can be used to add news items. A search news item object 514can be used to search existing news items. An edit news item object514.02 can be used to edit the news items that turned up in the search.A preview newsroom object 516 can be used to preview the appearance ofthe application 30 as currently modified by the content provider 22.

2. Calendar of Events

A calendar of events object 520 allows the content provider 22 to managethe events application 122. The calendar of events application 122 canbe used to manage the calendar at all levels of an organization. An addevent item object 522 can be used to add event items. A search eventitem object 524 can be used to search existing event items. An editevent item object 524.02 can be used to edit the event items that turnedup in the search. A preview event object 526 can be used to preview theappearance of the application 30 as currently modified by the contentprovider 22. An event registration object 528.02 can be used to sign upfor a particular event 88, so long as such a registration is inaccordance with any business rules 80 regarding registration.

3. Opportunities

An opportunities object 530 allows the content provider 22 to manage theopportunity application 124. The opportunity application 124 can be usedto publish and receive opportunity information on behalf of theorganization. An add opportunities object 532 can be used to addopportunity items. A search opportunities item object 534 can be used tosearch existing opportunities. An edit opportunities object 534.02 canbe used to edit the opportunity items that turned up in the search. Apreview opportunity object 536 can be used to preview the appearance ofthe application 30 as currently modified by the content provider 22. Anopportunities output object 538 can be used to allow users 50 to viewopportunities. An attach submission object 538.02 can be used to respondto the opportunity by attaching a resume, business plan, offer letter,purchase order, or some similar type of document.

4. Project Portfolio

A project portfolio object 540 allows persons affiliated with anorganization to manage projects using the project application 126discussed above. The project application 126 can be used to manage theprojects at all levels of an organization, subject to the parameters andconditions of the business rules 80. An add project object 542 can beused to add new projects. A search project object 544 can be used tosearch existing projects. An edit project object 544.02 can be used toedit the projects that turned up in the search. A preview project object546 can be used to preview the appearance of the project application 126as currently modified by the content provider 22. A project outputobject 548 can be used to implement in the “production environment” theversion of the project that is visible from the preview object 546.

5. Biography

A biography object 550 allows persons affiliated with an organization tomanage the display of biographical information using the biographyapplication 135 discussed above. The biography application 135 can beused to manage the biographies of persons and groups at all levels of anorganization, subject to the parameters and conditions of the businessrules 80. An add biography object 552 can be used to add newbiographies. A search biography object 554 can be used to searchexisting biographies. An edit biography object 554.02 can be used toedit the biographies that turned up in the search. A preview biographyobject 556 can be used to preview the appearance of the biographyapplication 135 as currently modified by the content provider 22. Abiography output object 558 can be used to implement in the “productionenvironment” the version of the biography that is visible from thepreview object 546.

6. Frequently Asked Questions

A frequently asked questions (FAQ) object 560 allows persons affiliatedwith an organization to manage the display of “frequently askedquestions” using FAQ module of the communication application 130discussed above. The FAQ application or module can be used to manage theFAQs to be asked of groups at all levels of an organization (subject tothe parameters and conditions of the business rules 80). An add FAQobject 562 can be used to add new FAQs. A search FAQ object 564 can beused to search existing FAQs. An edit FAQ object 564.02 can be used toedit the FAQs that turned up in the search. A preview FAQ object 566 canbe used to preview the appearance of the FAQ application as currentlymodified by the content provider 22. An FAQ output object 568 can beused to implement in the “production environment” the version of the FAQthat is visible from the preview object 546.

7. Document Library

A document library object 570 can be incorporated into the system 20 tomanage access to documents, the ability to change documents, anddocument histories. The document library object 570 facilitates thefunctionality of the document library application 128. An add documentobject 571 can create entirely new documents. A search document object572 can be used to search documents that already exist. A wide varietyof search criteria can be utilized by the search document object 572.Documents located in the search can be edited by an edit document object572.02. A preview document object 573 can be used by the contentprovider 22 to preview the changes made to the document, e.g. to seewhat the document would look like if it was saved as currently modified.An audit document object 574 can be used to audit those persons who haveaccessed the particular document. A document history object 575 can beused to track changes made to a document, and the various authors ofthose changes. A document types object 576 can be used to create,modify, and delete document types, e.g. categories of documents that canbe used to distinguish the processing the system 20 and the businessrules 80 used by the system 20. A document viewer object 577 allowspersons to view documents stored on the system 20.

8. Category Management

Categories provide a useful way to fully normalize data. The ability toorganize information in different categories allows the system 20 tosupport highly automated processing that is also highly configurable.Categories are stored on a categories database table that is describedin greater detail below. A category management object 580 allows contentproviders 22 and administrators to manage category classifications. Anadd category object 582 can be used to create new categories. A searchcategory object 584 can be used to search among existing categoryobjects. An edit categories object 584.02 can be used to edit thosecategories that already exist.

9. Administrative Console

An administrative console object 590 provides the functionality of theportals in the interface subsystem 90. A manager console object 592 canbe used to access lists of group managers through a group manager object592.02, lists of application managers through an application managerobject 592.04, and lists of header managers through a header managerobject 592.06. A delete manager object 592 can be used to remove variouspersonnel from one or more management roles. A portal management object596 can be used to configure and manage various portals. Many businessrules 80 can be configured through this object. A style manager objectcan be used to manage the portal templates and portal styles asdescribed in greater detail above.

10. Catalog

A catalog object 600 is means for managing online catalogs of productsand services (collectively “products”). A configure catalog object 601can be used to configure the catalog application 134. A manufacturersobject 602 can be used to interact with manufacturer informationrelating to the various products and services. An add products object603 can be used to add new products and services to the web site. Anedit products object 604 can be used to modify or delete products thatalready exist on the web site catalog 134. A product output view object605 allows the content provider to preview what the new modified catalog134 will look like if the changes are implemented in a runtimeenvironment. A product output search object 606 allows users 50 tosearch the catalog using various search tools.

11. E-Mail Broadcast

An email broadcast object 620 can be used to manage functionalityrelating to e-mail broadcasts from the web site. An add broadcast object612 can be used to create a new broadcast. A search broadcast object 614can be used to search existing broadcasts. An edit broadcast object614.02 can be used to modify broadcasts contained in the search resultsof a search. An add registration object 615 allows administrators tocreate sign-up interfaces so that users 50 can sign up for variousbroadcasts. A search registration object 616 allows administrators tosearch registration lists for certain registrants. An edit registrationobject 616.02 allows for the modification of registration information. Aregistration input object 617 can be used by users 50 to register for abroadcast. A broadcast generator object 618 can be used to actuallygenerate and transmit the various broadcasts.

As described in the communications applications 130, broadcasts need notbe limited to e-mails.

12. Surveys

A survey object 620 can perform the functionality of the surveyapplication 132. An add surveys object 622 can be used to create newsurveys. A search surveys object 624 can be used to perform searches forexisting surveys using a variety of search tools and search criteria. Anedit surveys object 624.02 can be used to edit any of the surveys in thesearch result. A survey input object 626 can be used to capture surveyinputs from users 50.

A reports object 628 can automatically generate a wide variety ofdifferent reports relating to the survey inputs. A survey summary object628.02 can provide a summary report in one of various predefined formatsin accordance with the business rules 80. A survey detail object 628.04can provide more detailed reports. An answer detail object 628.06 is forstoring the actual responses provided by the users 50. A time comparisonobject 628.08 can track the amount of time spent with each answer.

13. Newsletter

A newsletter object 630 can perform the functionality of the newsletterapplication 120. An add newsletter object 632 can be used to create newnewsletters or to create new newsletter content. A search newsletterobject 634 can be used to conduct searches on existing newslettercontent. A content manager object 636 can be used to manage the contentof the newsletter. A link existing content object 636.02 can be used tolink existing content. A link external content object 636.04 can be usedto link to external content. A create/edit custom content object 636.06can be used to add or modify customized newsletter content. An order allcontent types object 636.08 can be used to put together various contentsinto the unit of a newsletter.

IX. Database Table View

FIG. 14 is a data diagram illustrating one example of some of the database tables that can be incorporated into the system. The tables in FIG.14 illustrate a fully normalized embodiment of the system 20.De-normalized embodiments of the system 20 may also be implemented.Different embodiments may include different tables, with differentrelationships between the various tables.

A. Group Table

A group table 700 is used to store information relating toorganizational hierarchy. All subgroups in a subgroup table 702 exist asgroups in the group table 700, permitting a fully recursiverelationship. Thus, there are potentially no limits to the number oflayers in an organizational hierarchy. Thus, an organization can havemany groups, and those groups can have sub-groups, and so on and soforth. Some groups are organizations, while other groups are varioussubcategories such as groups or subgroups of organizations. The Group IDof the group table 700 is a foreign key on many other tables. Mostsystem 20 processing can be broken down into the various organizationhierarchies.

B. SubGroup Table

A subgroup table 702 works in conjunction with the group table 700 topermit multi-level organizations. The subgroup table 702 stores allparent-child relationships with respect to groups. Substantive datarelating to any particular group is stored in the group table 700.

C. Status Table

A status table 704 is used to store various status states that can beused by the system. The key to the status table can be a foreign key inmany different tables. In a preferred embodiment, the statuses supportedby the system 20 are inactive and primarily active.

D. Group Role Table

A group role table 706 can be used by the system 20 to store variousroles associated with a particular group. Similar to profiles, roles candetermine how individuals interact with the system 20, and the types ofcontent that can be accessed or updated.

E. Biography Table

A biography table 708 is used to support the functionality of thebiography application 30. All input characteristics relating to thebiography application described above are stored on this table.

F. Group Section Table

A group section table 710 is used by the system 20 to divide a groupinto sections. Unlike subgroups, a section cannot have subsections. In apreferred embodiment, a section does not belong to more than one group.Sections provide an additional way to modularize system 20functionality.

G. Group Report Table

A group report table 712 is used by the system 20 to store reportformats at the group level, another example of the highly modularizedfunctionality of the system 20.

H. Group Permission Table

A group permission table 714 is used by the system 20 to store andprocess functionality and data permissions associated with a particulargroup.

I. Group Member Permission Table

A group member permission table 716 links to group permission table 714,and allows distinctions based on individual identity.

J. Document Permission Table

A document permission table 718 stores all information relating to theability of groups and individuals to access documents, or tocreate/modify/delete documents.

K. Documents Table

A documents table 720 is for storing information relating to thedocuments themselves. In some embodiments, all document information islocated directly in the documents table 720. In other embodiments, thedocuments table may contain links to files stored elsewhere in thesystem 20.

L. Header Table

A header table 722 is used for storing header information used by thesystem 20. Headers can be associated with sections on the web site.

M. Application Table

An application table 724 is used to store information relating to theapplications 30 used by the system 20. The application table 724 can belinked to the group table 700, making applications dependent on groupaffiliation.

N. Documentation Types Table

A documentation types table 726 stores all of the different documenttypes that can be created by content providers 22 and administrators, asdiscussed above. By categorizing documents into various document types,automation and configurability are facilitated.

O. User Types Table

A user types table 728 can store various categories of users 50 for thepurposes of security (e.g. user types are not the same thing as userroles). These distinctions can be used by the business rules 80 tofacilitate the flexibility and automation of the system 20.

P. Products Table

A products table 730 is used to store the products and services listedin the catalog application 134. Products in the products table 730 canbe affiliated with particular groups in the groups table 700.

Q. Security Table

A security table 732 can link with the user types table 728 indetermining the functionality and data that is available to anyparticular individual utilizing the system 20.

R. Group Category Table

A group category table 734 can be referred to simply as the categorytable. The category table provides a means for further normalizing datawithin a group or sub-group unit.

S. Group Member Table

A group member table 736 is used to store lists of individuals whobelong to the various groups stored in the groups table 700.

T. Group Header Table

A group header table 737 is a table that links particular headers fromthe header table 722 to particular groups in the group table 700.

U. Document History Table

A document history table 740 stores the change history of the document,as discussed in greater detail above.

V. Document Audit History Table

A document audit history table 742 stores a history of every person whochanges a document. In alternative embodiments, merely accessing thedocument will result in being listed on this table.

W. Group Application Header Table

A group application header table 744 links a particular application to aparticular group and a particular header.

X. Group Member Application Table

A group member application table 746 lists group members who are allowedto access particular applications associated with a particular group.

X. Alternative Embodiments

In accordance with the provisions of the patent statutes, the principlesand modes of operation of this invention have been explained andillustrated in multiple preferred and alternative embodiments. However,it must be understood that this invention may be practiced otherwisethan is specifically explained and illustrated without departing fromits spirit or scope.

1. A system, including a computer, for managing content displayed on aweb site viewable by users of the web site through browser or mobileapplication, the system comprising: a plurality of configurableapplications administered by the computer, wherein: each configurableapplication includes a category of content stored by the computer anddisplayable to users of the web site, one of the plurality ofconfigurable applications is a biography application comprisingbiographical information about users of the web site, at least one ofthe plurality of configurable applications is generated by the computerat least in part based on inputs received from users of the web site,and the inputs include at least one of text, graphics, sounds,documents, and multi-media content; a first configurable link on the website that points to the biography application; and a second configurablelink on the web site that points to at least one of the plurality ofconfigurable applications, wherein: the computer includes a portalthrough which a user acting as an administrator can manage at least oneuser-configurable business rule that permits the user acting as anadministrator to selectively control the content viewable by other usersof the web site, the computer automatically generates the firstconfigurable link according to at least one rule that is configurable bya first user acting as an administrator, the computer automaticallygenerates the second configurable link according to at least one rulethat is configurable by the first user acting as an administrator, andat least some displayable content is generated by the computer based atleast in part on a user-configured business rule that managesdisplayable content for one of the plurality of configurableapplications by selecting from among the content stored by the computerbefore the displayable content generated by the computer is sent.